bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Mon, 31 Jul 2023 20:16:10 +0000 (21:16 +0100)
committerGianfranco Costamagna <locutusofborg@debian.org>
Mon, 31 Jul 2023 20:16:10 +0000 (21:16 +0100)
commit3b71afdb4fcbbfc8721c7b095998714144d552a7
tree2828777c487df7070752a7d56f9c5b39d9459ed0
parent392ae5c26e4a9ef8b1b8736147137680fd0a738d
bootstrap-fix-include-next

When doing a bootstrap, we use a newly built clang.
When this one is used, if already installed on the system,
we have clang header in two places:
llvm-toolchain-7-7/build-llvm/lib/clang/7.0.0/include/inttypes.h
and
/usr/include/clang/7.0.0/include/inttypes.h

Because clang expects only one of his headers to be available, it uses
include_next to get the glibc (libc6-dev package) header.

However, in the previous example, because we have inttypes.h twice in the
include search path, clang's header will call itself without any effect.
Therefore, it will do include_next until the define from the libc is existing (ex: _INTTYPES_H)

Gbp-Pq: Name bootstrap-fix-include-next.diff
clang/lib/Headers/inttypes.h
clang/lib/Headers/limits.h